Skip to content

Conversation

franzwilding
Copy link
Contributor

Q A
Bug fix? yes
New feature? no
Docs? no
Issues
License MIT

When passing agent options to an internal agent call, the tools array is already resolved and is no longer just an array of strings. As a result, the input processor no longer filters the available agent tools. I’m not sure if this behavior is intentional, but in my case it causes issues: with each internal call, all tools suddenly become available, which confuses the model.

@carsonbot carsonbot added Bug Something isn't working Status: Needs Review labels Sep 29, 2025
@carsonbot carsonbot changed the title Passing filtered tools option for internal agent calls Passing filtered tools option for internal agent calls Sep 29, 2025
@franzwilding franzwilding changed the title Passing filtered tools option for internal agent calls [Agent] Passing filtered tools option for internal agent calls Sep 29, 2025
@chr-hertel
Copy link
Member

Hey, okay, sounds fishy, are you referring to an agent using a different agent as a tool or what is an "internal agent"?

@franzwilding
Copy link
Contributor Author

No, just regular tool calling. Once, one model does not successfully run, the inner agent->call is triggered and at this time, the tools are already resolved.

@franzwilding
Copy link
Contributor Author

@chr-hertel I think this only happens, if we have an event without an result. In this case, the AgentProcessor will call the agent again:
$result = $event->hasResponse() ? $event->result : $this->agent->call($messages, $output->options);

@chr-hertel
Copy link
Member

Do you have a way how I could reproduce this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Status: Needs Review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants